All committers have signed the CLA.

Codecov Report

Merging #2760 (3df55b7) into v4 (4ab1f21) will decrease coverage by 0.28%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##               v4    #2760      +/-   ##
==========================================
- Coverage   93.77%   93.48%   -0.29%     
==========================================
  Files          34       34              
  Lines        1333     1336       +3     
  Branches      381      382       +1     
==========================================
- Hits         1250     1249       -1     
- Misses         81       85       +4     
  Partials        2        2              

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4ab1f21...3df55b7. Read the comment docs.

Can you provide example the problem? Maybe screenshot(s)?

Some why "message" object format is changed when I switch from webpack v4.44.2 to v5.0.0.
Instead of string Array now it is Array of objects with only "message" property.

Hi, @evilebottnawi
I am new on Github and newb with all this Nodejs and related stuff.
I have no idea even how to run and pass all those tests/checks.
I do not know is this issue should be addressed in webpack-dev-server or in webpack or some webpack's dependency.
I hope the issue is pretty clear for you, and if you could assist/help with it - I will appreciate it...
Please let me know if you need some more information.

Thanks!

@Xrumet Did you also updated webpack-cli? I had an issue with the dev-server and webpack 5 but I downgraded webpack-cli back to 3.3.12 and it was all fine.

@phara0hcom No, I am using Node API to start dev server, so I had removed webpack-cli at all.
Not sure, is it important, my dev-server configuration is in webpack config like that:
devServer:{
....
overlay: {
errors: true,
warnings: false
},
...
}

@Xrumet Ok, could you try to install webpack-cli npm install -D webpack-cli
https://github.com/webpack/webpack-cli#about
If I read this then I think you need it.

@phara0hcom sure, I have already tried it right after your previous comment.
I have installed webpack-cli v3.3.12 and also run my project with CLI instead of API.
Behavior is the same. I see error overlay itself. But, because error "data" format is changed - "entities.encode" or "ansiHTML" checks input string for "length" property (expecting a string but object is passed) and returns empty string.

So, I see "Build failed." message but do not see errors/warnings list.

Hi @evilebottnawi
Could you help with this fix?
I have try to run npm install on my windows and it failed some why.
So, I cannot even try to write and check unit tests to pass code coverage policy.

Seems like that's it for me :(

@Xrumet Hi, can you rebase?